-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(deps): update rust crate axum to 0.7.3 #29
Conversation
93e1e01
to
3149460
Compare
3149460
to
4478def
Compare
hyper got rid of server in v1.0 and so did axum. From changelog:
|
Signed-off-by: simonsan <[email protected]>
Signed-off-by: simonsan <[email protected]>
Signed-off-by: simonsan <[email protected]>
Signed-off-by: simonsan <[email protected]>
…ad of using `first()` Signed-off-by: simonsan <[email protected]>
Edited/Blocked NotificationRenovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR. You can manually request rebase by checking the rebase/retry box above. ⚠ Warning: custom changes will be lost. |
This PR contains the following updates:
0.6.20
->0.7.3
Release Notes
tokio-rs/axum (axum)
v0.7.3
: axum - v0.7.3Compare Source
Body
implementsFrom<()>
now (#2411)tracing
feature by default (#2460)serve
(#2398)RouterIntoService
implementsClone
(#2456)v0.7.2
: axum - v0.7.2Compare Source
axum::body::to_bytes
(#2373)serve
(#2400)v0.7.1
: axum - v0.7.1Compare Source
v0.7.0
: axum - v0.7.0Compare Source
WebSocketUpgrade::max_send_queue
(i.e. the
B
type param has been removed) (#1751 and #1789):FromRequestParts
FromRequest
HandlerService
HandlerWithoutStateExt
Handler
LayeredFuture
Layered
MethodRouter
Next
RequestExt
RouteFuture
Route
Router
hyper::Body
as that type is removedin hyper 1.0. Instead axum has its own body type at
axum::body::Body
(#1751)extract::BodyStream
has been removed asbody::Body
implements
Stream
andFromRequest
directly (#1751)sse::Event::json_data
to useaxum_core::Error
as its error type (#1762)DefaultOnFailedUpdgrade
toDefaultOnFailedUpgrade
(#1664)OnFailedUpdgrade
toOnFailedUpgrade
(#1664)TypedHeader
has been move toaxum-extra
(#1850)Empty
andFull
. Useaxum::body::Body::empty
andaxum::body::Body::from
respectively (#1789)IntoResponse::into_response
must useaxum::body::Body
as the body type.axum::response::Response
does this(#1789)
BoxBody
type alias and itsbox_body
constructor. Use
axum::body::Body::new
instead (#1789)RawBody
extractor.axum::body::Body
implementsFromRequest
directly (#1789)http-body
no longer implementIntoResponse
:Full
, useBody::from
insteadEmpty
, useBody::empty
insteadBoxBody
, useBody::new
insteadUnsyncBoxBody
, useBody::new
insteadMapData
, useBody::new
insteadMapErr
, useBody::new
insteadaxum::extract::Request
type alias where the body isaxum::body::Body
(#1789)Router::as_service
andRouter::into_service
to workaroundtype inference issues when calling
ServiceExt
methods on aRouter
(#1835)axum::Server
as it was removed in hyper 1.0. Insteaduse
axum::serve(listener, service)
or hyper/hyper-util for more configuration options (#1868)Router::nest
.Routers nested with
Router::nest_service
will no longer inherit fallbacks (#1956)Sec-WebSocket-Key
header inWebSocketUpgrade
(#1972)axum::extract::Query::try_from_uri
(#2058)IntoResponse
forBox<str>
andBox<[u8]>
([#2035])MethodFilter
. It no longer uses bitflags (#2073).source()
of composite rejections (#2030)#[debug_handler]
(#2014)IntoResponse
for(R,) where R: IntoResponse
(#2143)NestedPath
extractor (#1924)handle_error
function to existingServiceExt
trait (#2235)impl<T> IntoResponse(Parts) for Extension<T>
now requiresT: Clone
, as that is required by the http crate (#1882)axum::Json::from_bytes
(#2244)FromRequestParts
forhttp::request::Parts
(#2328)FromRequestParts
forhttp::Extensions
(#2328)DefaultBodyLimit
to individual routes (#2157)Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.